Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add web3/metamask-compatible personal_sign and personal_recover, fixes #18 #30

Merged
merged 2 commits into from
Aug 5, 2018

Conversation

buhrmi
Copy link
Contributor

@buhrmi buhrmi commented Jul 22, 2018

No description provided.

@buhrmi buhrmi changed the title Add web3/metamask-compatible personal_sign and personal_recover Add web3/metamask-compatible personal_sign and personal_recover, fixes #18 Jul 23, 2018
@buhrmi
Copy link
Contributor Author

buhrmi commented Jul 23, 2018

This should resolve #18

@se3000
Copy link
Owner

se3000 commented Jul 30, 2018

Awesome! Thank you for spearheading this.

One thing: I've been trying to move towards accepting and returning binary data in hex. Could you switch the API to match that?

@buhrmi
Copy link
Contributor Author

buhrmi commented Jul 30, 2018

done

@buhrmi
Copy link
Contributor Author

buhrmi commented Aug 3, 2018

what's the holdup?

@se3000 se3000 merged commit 82e89b3 into se3000:master Aug 5, 2018
@se3000
Copy link
Owner

se3000 commented Aug 5, 2018

This is a side project, so it's a bit hard to find the time to give this the thought it needs.

Anyway, thanks for the contribution and for your patience. Just bumped the version and released the newest gem.

🍻

@buhrmi
Copy link
Contributor Author

buhrmi commented Aug 6, 2018

awesome. yeah I totally get it. It's an amazing gem for a side project.

anyways, now the method signature is not in line with the rest of the API (expecting hex parameters whereas the rest of the API is still expecting binary). ah well. good enough :P

@se3000
Copy link
Owner

se3000 commented Aug 7, 2018

Thanks, happy it's getting some usage!

I'm only really moving towards hex strings. Added the tx_data_hex configuration option a few minor versions back. I'd like to get all parts of the gem using it for consistency's sake, but like I said, tight on time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants